Repository navigation
fix: Separate logical replication byte-distance alerts - #276
Merged
Merged
Conversation
philippemnoel
force-pushed
the
dev
branch
2 times, most recently
from
October 5, 2026 03:37
3448db7 to
c01e6b2
Compare
philippemnoel
force-pushed
the
fix/alert-parity-logical-distance
branch
from
October 5, 2026 03:46
9bc97ee to
4204fe0
Compare
philippemnoel
force-pushed
the
fix/alert-parity-logical-distance
branch
from
October 5, 2026 05:51
4204fe0 to
af27ae5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add dedicated logical WAL-position distance alerts matching MCC's thresholds: above 1 GiB for five minutes, or above 4 GiB for two minutes. Retain pod, database, and subscription identity. These alerts use existing CNPG exporter metrics without a kube-state-metrics dependency.
Complements merged #270, which separated receipt-age alerts from byte-distance checks. The runbook follows the standard Description, Impact, Diagnosis, and Mitigation structure and explains that this position gap does not measure unapplied work or committed apply progress.
Validation: Helm lint, the existing Prometheus-rule rendering suite, alert exclusions, and
git diff --checkpassed. Temporary vmalert-tool v1.148.0 fixtures passed zero/negative gaps, exact warning/critical boundaries, warning-only and critical gaps, same-named subscriptions in separate databases, and missing worker metrics.The dedicated alert-parity-logical-distance Chainsaw suite was removed. Full Kubernetes integration remains for CI. No deployment was performed. Chart versions are generated by the publishing workflow.